Skip to content

[SSF-134]: Update FM Management Frontend#104

Open
dburkhart07 wants to merge 35 commits intomainfrom
ddb/SSF-134-update-fm-management-frontend
Open

[SSF-134]: Update FM Management Frontend#104
dburkhart07 wants to merge 35 commits intomainfrom
ddb/SSF-134-update-fm-management-frontend

Conversation

@dburkhart07
Copy link

ℹ️ Issue

Closes #134

📝 Description

  • Created frontend design for the FM Management, including the page and new donation modal
  • Adjusted the backend to add a food rescue field, which is now available in the modal
  • Used some specific date calculations to ensure that a UI-friendly date picker is easily converted to an understandable format in our donation entity for recurring donations.

✔️ Verification

Took screenshots of the pages:
image
image
image

Verified each updated endpoint worked on Postman

🏕️ (Optional) Future Work / Notes

We will need to update this later on when we go to finish up the Action Required tab.

@@ -42,46 +49,30 @@ export class DonationsController {
type: 'object',
properties: {
foodManufacturerId: { type: 'integer', example: 1 },
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

NOTE FOR PR Reviewer: We deleted this since it does not make sense to have either of these fields here in creating a donation. The status will always be the same, as will the date donated.

Copy link
Author

@dburkhart07 dburkhart07 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Leaving comment for PR reviewer

@amywng amywng self-requested a review February 15, 2026 22:45
@dburkhart07 dburkhart07 requested a review from amywng February 16, 2026 20:04
};
setCurrentPages(initialPages);
} catch (error) {
alert('Error fetching donations: ' + error);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

might need to change depending on when justin's alert pr goes in

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will keep this comment unresolved till then.

Copy link
Member

@amywng amywng left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and frontend things! 💐

@dburkhart07 dburkhart07 requested a review from amywng February 18, 2026 05:51
@maxn990 maxn990 self-requested a review February 18, 2026 15:19
>
{parseInt(endsAfter) > 1
? 'Occurrences'
: 'Occurrence'}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wait instead of making the number as big as "occurrence" can you make them both smaller to match the rest of the fields

import AdminOrderManagement from '@containers/adminOrderManagement';
import { Amplify } from 'aws-amplify';
import CognitoAuthConfig from './aws-exports';
import { Button } from '@chakra-ui/react';
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems to be some unnecessary imports


@Get('/:donationId')
@Get('/by-fm-id/:foodManufacturerId')
async getDonationsByFoodManufacturer(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think we can probably write controller tests

display="inline-flex"
alignItems="center"
justifyContent="space-between"
backgroundColor={colors[0]}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think there could be a tad more room above each status title

textStyles,
tokens: {
colors: {
dashboardStatuses: {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think if you look in the figma these have actual names within the design system that fit into colors, e.g. blue 100, yellow hover, etc. so can you switch to putting them in the color categories. also i think your color for available is too dark

<Checkbox.Indicator />
</Checkbox.Control>
<Checkbox.Label color="neutral.700">
Make Donation Recurring
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we make this text not as bold?

size="md"
fontWeight={600}
>
Submit Donation
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this text should be white

validateId(foodManufacturerId, 'Food Manufacturer');

const manufacturer = await this.manufacturerRepo.findOne({
where: { foodManufacturerId: foodManufacturerId },
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need two foodManufacturerId's here since they're named the same thing

}
};

const generateNextDonationDates = (): string[] => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

perhaps we could move this to a utils and write tests for it...


<Table.Cell>
<Input
_placeholder={{ color: 'neutral.300' }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we move these stylings to a variable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments